Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
Important: Both peers must be using the same address family (IPv4 or IPv6) or the Service Redundancy Protocol (SRP) connection will not be established.checkpoint session duration duration
Specifies the amount of time (in seconds) that a call must be active before it is check pointed. duration must be an integer from 1 through 65535.
configuration-interval interval
interval must be an integer from 1 through 65535.
dead-interval interval
Specifies the amount of time (in seconds) for the dead interval. interval must be an integer from 1 through 65535.
delay-intervalinterval
Specifies the amount of time (in seconds) for the delay interval. interval must be an integer from 1 through 65535.
hello-interval interval
Specifies the lapse time (in seconds) between sending the hello message. interval must be an integer from 1 through 65535.
internal-switchover-retry-interval interval
Specifies the amount of time (in seconds) between internal switchover retries. interval must be an integer from 10 through 120.
Important: See the monitor authentication-probe, monitor bgp, or monitor diameter commands for more information on associated SRP monitoring.[ no ] monitor authentication-probe context context_name { ipv4_address | ipv6_address } [ port port_number ]
context context_name
context_name must be an existing context expressed as an alphanumeric string of 1 through 79 characters.
port port_number
Identifies a specific port for the authentication probe. port_number must be the port for the AAA server expressed as an integer from 1 through 65535.
The following example initiates the connection monitoring between the primary chassis and AAA server 10.2.3.4 at port 1025:
[ no ] monitor bfd context context_name { ipv4_address | ipv6_address } { chassis-to-chassis | chassis-to-router }
context context_name
context_name must be an existing context expressed as an alphanumeric string of 1 through 79 characters.
chassis-to-chassis | chassis-to-router
chassis-to-chassis: BFD runs between primary and backup chassis on non-SRP links.
chassis-to-router: BFD runs between chassis and router.
Important: BFD monitoring must run between chassis-to-chassis or chassis-to-router. context context_name
context_name must be an existing context expressed as an alphanumeric string of 1 through 79 characters.
vrf vrf_name
The following example initiates the connection monitoring between the primary chassis and BGP peer 125.2.1.56:
[ no ] monitor diameter context context_name endpoint endpoint_name [ fqdn fqdn | peer { ipv4_address | ipv6_address } ] [ port port_number ]
context context_name
context_name must be an existing context expressed as an alphanumeric string of 1 through 79 characters.
endpoint endpoint_name
endpoint_name must be for the Diameter server expressed as an alphanumeric string of 1 through 63 characters.
fqdn fqdn
fqdn must be for the Diameter server expressed an alphanumeric string of 1 through 127 characters.
port port_number
port_number must be the port for the Diameter server and an integer from 1 through 65535.
Important: Endpoint name, FQDN, IP address, and port must all match the Diameter protocol configured values for the peer state to be updated.The following example initiates the connection monitoring between the primary chassis and the Diameter server on context test1 and endpoint end2:
num-internal-switchover-retry retries
The number of times an internal switchover would be retried in case of standby chassis. retries must be an integer from 1 through 10.
Important: Both peers must be using the same address family (IPv4 or IPv6) or the Service Redundancy Protocol (SRP) connection will not be established.The following example specifies 10.2.3.4 as a backup peer system to the primary system:
Important: priority takes affect only during simultaneous initializing of all chassis in an ICSR configuration, and only if a misconfiguration has both chassis in the same mode (both Primary or both Backup).priority priority_value
priority_value must be an integer from 1 through 255, where 1 is the highest priority.
This command determines which chassis transitions to the Active state when all chassis have the same mode configuration. priority acts as a tie breaker for the state determination only when all chassis initialize simultaneously. The chassis with the higher priority (lower number) becomes Active, while the chassis with the lower priority (higher number) becomes Standby.
route-modifier threshold threshold_value
Specifies the value that causes the route-modifier counter to be reset to the initial value. threshold_value must be an integer from 2 through 32.
